Skip to content

fix(oracle): use IPv6 subnet prefix for secondary VNIC addresses#6843

Open
qm3ster wants to merge 1 commit intocanonical:mainfrom
qm3ster:fix/oracle-ipv6-prefix-length
Open

fix(oracle): use IPv6 subnet prefix for secondary VNIC addresses#6843
qm3ster wants to merge 1 commit intocanonical:mainfrom
qm3ster:fix/oracle-ipv6-prefix-length

Conversation

@qm3ster
Copy link
Copy Markdown

@qm3ster qm3ster commented Apr 17, 2026

On OCI instances with IPv6 enabled on a secondary VNIC, _add_network_config_from_opc_imds used a single network variable (derived from the IPv4 subnetCidrBlock) for both IPv4 and IPv6 prefix lengths. This caused the IPv6 address to be configured with the IPv4 prefix length.

OCI's IMDS provides ipv6SubnetCidrBlock with the correct IPv6 prefix, but it was never read.

The fix moves the network assignment inline to each address block, so IPv4 uses subnetCidrBlock and IPv6 uses ipv6SubnetCidrBlock.

On dual-stack secondary VNICs, the IPv6 address was incorrectly
configured with the IPv4 subnet prefix length (e.g. /24 instead
of /64). This happened because `network` was computed from
`subnetCidrBlock` (IPv4) and reused for both address families.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant